-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: add nameserver 1.1.1.1 to conformance-runtime test LVM #29455
Conversation
bd1bdb0
to
b1d7bc0
Compare
/ci-runtime |
With the removal of setting a nameserver via the little-vm-helper GitHub action, conformance-runtime tests are failing quite often with the following error. ``` dial tcp: lookup quay.io on 127.0.0.53:53: read udp 127.0.0.1:40553->127.0.0.53:53: read: connection refused ``` The assumption is that the local DNS resolver isn't ready at that time when pulling the image. Therefore, this way temporarily re-adds the nameserver `1.1.1.1` manually. See: cilium/little-vm-helper#118 Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
The property dns-resolver has been removed from the little-vm-helper GitHub action. Therefore, this commit removes the usage of it in the cilium repository. See: cilium/little-vm-helper#118 Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
b1d7bc0
to
357fe69
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good find! Shall we bring back the custom resolver setting to the LVH action?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I don't think it's necessary. All other cases that use the LVH are working fine. @brb I think it would be better to check the status of the resolver in the VM before allowing commands via the github actions API. e.g. solving in the LVH. WDYT? |
SGTM. |
FYI, I've marked this PR to be backported to |
With the removal of the property
dns-resolver
to set a nameserver via the little-vm-helper GitHub action, conformance-runtime tests are failing quite often with the following error.The assumption is that the local DNS resolver isn't ready at that time when pulling the cilium docker plugin image (rather early after startup).
Therefore, this commit temporarily re-adds the nameserver
1.1.1.1
manually in the runtime test - at the beginning of/etc/resolv.conf
- and therefore prioritized.See: cilium/little-vm-helper#118